5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
- Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-15: Using the Image Editor

Image Item Specifications


If you are editing an existing item or adding a new item, APPX presents a number of specification screens that establish various operational and display attributes, as well as data lookup definitions.

The item screen contains specifications that relate to the appearance of a data dictionary field on an input, output, or inquiry image. The specifications that follow are a composite of those you see when defining an input, output, or inquiry item. If a specification only displays for a specific type of process, the definition indicates so. The Item screens, shown The Inquiry Record Frames Additional Attributes overlay is shown below., displays when you choose to place a field on an image by selecting add or change mode for item definition.

Input or Inquiry Key Entry Item Screen for Alphanumeric, Date, and Logic Fields

Input or Inquiry Key Entry Item Screen for Numeric Fields

Output or Inquiry Item Screen for Alphanumeric, Date, or Logic Fields

Output or Inquiry Item Screen for Numeric Fields

The item screens contain some of the following fields, depending on the type of process.

Field Name identifies a specific field (by application ID, field name, and occurrence) to be painted on an image. Predefined fields can also be painted on an image; their application ID is ---.

Modifiable? for input processes and inquiry Key Entry images, governs whether or not a user is permitted to change the value that displays. If 'no' (blank), APPX determines whether the item is modifiable, based upon the operational phase. If the operational phase is live operations, the item is not modifiable. If the operational phase is initial setup or recovery processing, the item is modifiable. The default is 'yes' .

Required? for input processes and inquiry Key Entry images, determines whether or not a user is required to enter a value. The default is 'no' .

Blank If Zero? indicates whether or not a value of 0 should display as a blank (rather than a 0) to a user. The default is 'no' .

Right Justify? governs whether or not the contents of the item should align with the far right-hand character position in the mask. If 'no' , the contents are aligned with the far left-hand character position in the mask. For input processes, the default is 'no' . For output processes, the default is 'yes' .

Auto Increment, for input processes, indicates that the default value for the item on each record added should be automatically incremented by the value that you enter here.

Auto-Total Type, for output processes, indicates whether or not the item is to be automatically totaled by APPX and, if so, the type of total. The Auto Total Type options are:

0 = None. The value in this numeric item for each record is not automatically totaled by the output process.

1 = Sum. The value in this numeric item for each record is automatically added together, and the total is printed for any subtotals or grand totals in the output.

2 = Hash. The value in the first 16 characters of this numeric item for each record is automatically added together, and the total is printed for any subtotals or grand totals in the output. Hash totals ignore overflow. For example, if an item is five characters in length, adding one to 99999 results in a value of 0. Numeric items that are hash-totaled must be defined as packed decimal storage type in the data dictionary.

The default is 0 = None.

Extra Digits Left, for output processes, designates a number of digits (in addition to the digits in the data dictionary) to allow for the potentially greater size of totaled fields.

The following options are available at the bottom of every Item screen:

Data Lookup - See Data Lookup Option for details.

Additional Attributes - See Image Item Additional Attributes Option for details.

Toolbox - See Image Item Toolbox Option for details.

GUI Attributes varies depending on the type of field (alphanumeric, numeric, date, or logic) and the type of process. See the Defining Graphical Attributes for Image Fields section in Using GUI Features of the Image Editor.

Application Design Manual                                         "Powered by Appx Software"

424

©2006 By APPX Software, Inc. All Rights Reserved